Summary

ReverbCode can now turn an explicitly eligible tracker issue into exactly one worker session for a registered project. This completes the first issue-intake slice from #422 while keeping the tracker read-only: the daemon polls configured projects, applies label/assignee eligibility, stores the canonical issue id on the session, and lets the existing session/PR/lifecycle machinery take over.

The intake loop is defensive by default. Existing projects are unaffected unless they opt in, duplicate sessions are skipped across daemon restarts, provider/spawn failures back off instead of blocking the daemon, and oversized issue bodies are truncated so the generated worker prompt stays within the session prompt limit.

This also wires the project config through the API/client schema and CLI config path so the feature has one durable configuration surface instead of frontend-only behavior.

Closes #422.

Scope Notes

• This phase is read-only toward the tracker: no comments, status transitions, or webhook receiver.
• Eligibility is intentionally explicit: enabled intake requires at least one label or assignee rule.
• The existing session list/API carries the issue-linked session through issueId; richer dashboard controls and visual affordances are left for follow-up work.
• Frontend build validation is kept green by making the documented npm run build path package the daemon and Electron app successfully.

Validation

• npm run lint
• cd backend && go test -race ./...
• cd backend && go vet ./...
• npm run frontend:typecheck
• npm --prefix frontend test -- --run
• npm --prefix frontend run build